Process Modeling Using UML
نویسندگان
چکیده
The Unified Modeling Language (UML)1 is a visual, object-oriented, and multipurpose modeling language. Primarily designed for modeling software systems, it can also be used for business process modeling. Since the early 1970s, a large variety of languages for data and software modeling like entity-relationship diagrams [2], message sequence charts [5, 10], state charts [9], and so on, have been developed, each of them focusing on a different aspect of software structure or behavior. In the early 1990s, object-oriented design approaches gained increasing attention, for instance, in the work of James Rumbaugh (Object Modeling Technique or OMT [21]), Grady Booch [1], and Ivar Jacobson [12]. The UML emerged from the intention of Rumbaugh, Booch, and Jacobson to find a common framework for their approaches and notations. Furthermore, the language was also influenced by other object-oriented approaches like that of Coad and Yourdon [3]. The first version, UML 1.0 [20], was released in 1997 and accepted as a standard by the Object Management Group (OMG)2 the same year. The OMG, which took over the responsibility for the evolution of the UML from then on, is a consortium from both industry and academia and is also responsible for other wellknown initiatives like CORBA, MDA, and XMI. OMG specifications have to undergo a sophisticated adoption process before being agreed upon as a standard by the OMG members. Since many important tool builders and influential software companies are involved in the OMG, UML has quickly been accepted by the software industry, especially since version UML 1.3 appeared in 1999. When writing this book, the current UML version was UML 2.0 [18], a major revision of the language. UML is a conglomeration of various diagram types. Therefore, the challenge is to provide a uniform framework for all these heterogeneous diagram types and accounting for relationships between them. In UML, this is solved by a common meta-model that formally defines the abstract syntax of all diagram types. The
منابع مشابه
A Generic Approach to Reuse Unified Modeling Language Components Following an Agile Process
Unified Modeling Language (UML) is considered as one of the widespread modeling language standardized by the Object Management Group (OMG). Therefore, the model driving engineering (MDE) community attempts to provide reuse of UML diagrams, and do not construct it from scratch. The UML model appears according to a specific software development process. The existing method generation models focus...
متن کاملUML Modelling of Automated Business Processes with a Mapping to BPEL4WS
The Business Process Execution Language for Web Services (BPEL4WS) provides an XML notation and semantics for specifying business process behaviour based on Web Services. A BPEL4WS process is defined in terms of its interactions with partners. A partner may provide services to the process, require services from the process, or participate in a two-way interaction with the process. The Unified M...
متن کاملBusiness Process Modeling: Defining Domain Specific Modeling Languages by Use of UML Profiles
General-purpose modeling languages are inadequate to model and visualize business processes precisely. An enterprise has its own vocabulary for modeling processes and its specific tasks may have attached data that define the tasks precisely. We propose using Domain Specific Modeling (DSM) languages to model business processes, such that an enterprise can define its own DSM language(s) capturing...
متن کاملProcess-Integrated Refinement Patterns in UML
The Unified Modeling Language (UML) is a widely used standard in Model-Driven Engineering (MDE). Using the UML in a software development process means to refine and evolve models in many ways. Firstly, a system model evolves through different layers of abstraction towards an appropriate design in an object-oriented programming language (vertical refinement). Secondly, a set of consecutive revis...
متن کاملAvailability evaluation of Software architecture of object oriented Style using coloured Petri nets
Software architecture is one of the most fundamental products in the process of software development in the areas of behavioral or non- behavioral features like availability or transformability change. There are different ways to evaluate software architecture one of which is the creation of application model. An executable model of software architecture is an official description of architectu...
متن کاملOn formalizing UML and OCL features and their employment to runtime verification
Model-driven development (MDD) has been identified as a promising approach for developing software. By using abstract models of a system and by generating parts of the system out of these models, one tries to improve the efficiency of the overall development process and the quality of the resulting software. In the context of MDD the Unified Modeling Language (UML) and its related textual Objec...
متن کامل